Make nested interpretation logic part of the ExpressionStrategy interface#731
Open
jasmith-hs wants to merge 1 commit intomasterfrom
Open
Make nested interpretation logic part of the ExpressionStrategy interface#731jasmith-hs wants to merge 1 commit intomasterfrom
jasmith-hs wants to merge 1 commit intomasterfrom
Conversation
…e ExpressionStrategy interface
jasmith-hs
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
To allow for extensions of the ExpressionStrategy interface to more specifically determine whether nested interpretation should be performed.
cc @Joeoh
(This was supposed to open as a draft PR, but I guess I pressed some hotkey that opened the PR as I was typing the title)